Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1552

reference
989-tree-1
name
1552
tree-preservation-order

undefined

989-tpo-1
uprn
address-text
point
POINT (-1.017169 50.874851)
geometry
MULTIPOLYGON (((-1.017113 50.874845,-1.017115 50.874856,-1.017123 50.874866,-1.017135 50.874874,-1.017151 50.874880,-1.017169 50.874881,-1.017186 50.874880,-1.017202 50.874875,-1.017215 50.874867,-1.017223 50.874857,-1.017226 50.874846,-1.017224 50.874835,-1.017216 50.874825,-1.017204 50.874817,-1.017188 50.874811,-1.017170 50.874810,-1.017153 50.874811,-1.017137 50.874816,-1.017124 50.874824,-1.017116 50.874834,-1.017113 50.874845)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL